|
|
 |
|
|
|
|
129: End Function
130:
131:
132: Private Function BankAccountProduct_getProductID() As Byte
133: BankAccountProduct_getProductID = mb_ProductID
134:
135: End Function
136:
137: Private Sub BankAccountProduct_setProductID(argMsgID As Byte)
138: mb_ProductID = argMsgID
139: End Sub
140:
141:
142: Private Sub Class_Initialize()
143: 'm_pAccountType = TypeName(Me)
144: 'mb_ProductID = BankProducts.BasicPersonalChecking
145: mvarAccountNumber = 002
146: End Sub
147:
148: Private Sub Class_Terminate()
149: m_pAccountType =
150: mb_ProductID = 0
151: End Sub |
|
|
|
|
|
|
|
|
VERIFYING BUSINESS LOGIC SERVICES: IS THE DEVELOPMENT APPROACH EFFECTIVE? |
|
|
|
| | Developing business applications is quite complex because many business rules tend to be somewhat confusing or vague at times. This is specifically true for companies where business processes are very dynamic, sometimes volatile. This volatility reflects the fluidity of market forcessupply and demand. The development approach best suited for such dynamic changes is object-oriented programming, coupled with object-oriented analysis and design. That way, you can develop effective business policy enforcement classes that are able to more fully test preconditions and postconditions by encapsulated behavior. | | VALIDATING BUSINESS LOGIC SERVICES: IS THE SYSTEM DEVELOPED CORRECTLY FOR BUSINESS LOGIC? | | The answer to this question depends on how your client company, or you as an entrepreneur, views the success of your project. The best measure for correctness of development is in reusability and quality. Reusability can't be determined effectively until you use your classes in another application. Reusability and quality are enhanced by self-testing objects where methods test object and data types upon entry and exit of such methods, as well as how invariants, such as local variables in methods, are used. |
|
|